perm filename WKSHOP.DOC[NET,KMC] blob sn#156984 filedate 1975-04-28 generic text, type T, neo UTF8
13-FEB-75 14:34:49,462
Date: 13 FEB 1975 1434-PST
From: SHORTLIFFE
Subject: DOCUMENTATION FOR WORKSHOP DEMOS
To:   SRIDHARAN
cc:   VANMELLE
- - - -
SRI,
	THE FILE IN MY DIRECTORY NAMED MYCIN.DOC MAY BE THE KIND OF ON-LINE
PROGRAM DOCUMENTATION YOU MENTIONED IN YOUR LIST OF DESIRED ATTRIBUTES
FOR PROGRAM DEMONSTRATIONS IN JUNE.  WHAT I AM NOT CERTAIN ABOUT
IS WHAT IT WOULD TAKE TO MAKE IT AVAILABLE IN PROGRAM-READABLE FORMAT.
WHAT DID YOU HAVE IN MIND?
	TED

-------
11-MAR-75 15:58:07,641
Date: 11 MAR 1975 1558-PST
From: NSMITH
Subject: RECORD typescripts
To:   SRIDHARAN
- - - -
	I don't know if you have heard that Bob has in conjunction
with the DENDRAL group written a new version of RECORD.  It is
designed specifically for recording sessions of non-experienced
users.  The user never sees RECORD at all.  The call to RECORD
is put in the login.cmd file of the log-in directory.  The user
is asked if he/she minds being recorded and if not the pseudo-tty
is logged-in and the recording file opened.  The user runs whatever
program and at log-out both jobs are automatically logged-out.
			Nancy Smith
-------
12-MAR-75 16:47:03,1828
Date: 12 MAR 1975 1647-PST
From: CROSSLAND
Subject: RECORD
To:   SRIDHARAN
- - - -
(1)  PETER FRIEDLAND (SUMEX USER FRIEDLAND) HAS TAKEN
OVER THE SIMPLE VERSION OF RECORD AND IS MAINTAINING IT
FOR USE BY THE DENDRAL GROUP.  I WILL
MENTION TO HIM THAT YOU WOULD LIKE TO HAVE SOME INFORMATION
ABOUT IT.  IT SEEMS TO WORK TRANSPARENTLY, BUT IT IS
STILL NOT QUITE WHAT ONE WANTS -- A SYSTEM-LEVEL RECORDING
FEATURE.  THAT, HOWEVER, INVOLVES SYSTEM PROBLEMS
AND IS NOT LIKELY.

(2)  IT IS POSSIBLE TO MARK THE OUTPUT FILE IN THAT
WAY.  THERE ARE HOWEVER SOME PROBLEMS CONNECTED WITH ECHOING
AND WHAT PART OF THE DIALOGUE IS TYPED BY THE USER.
THIS IS BECAUSE RECORD WORKS BY TURNING OFF ECHOING IN THE SERVER
JOB, THEN PRINTING OUT WHAT IS RECEIVED FROM THE PTY.
WE OF COURSE KNOW WHAT THE USER HAS TYPED TO US BUT WE DONT KNOW
WHAT PART OF THE CHARACTERS COMING FROM THE PTY ARE ECHOES OF THE
USER INPUT AND WHAT PART ARE FROM THE PROCESSES IN
THE PTY JOB.  WHEN THE PTY ITSELF GOES INTO NON-ECHOING MODE,
THE SITUATION BECOMES MUCH WORSE.   (THE JSYSES THAT
WOULD TELL US THE STATUS OF THE PTY CANNOT BE EXECUTED
BY THE PTY JOB WITHOUT BEING ENABLED.)  

IF ONE ASSUMES THAT THE PTY JOB IS ALWAYS ECHOING THEN THE
ALGORITHM IS NOT TOO DIFFICULT BECAUSE YOU MATCH USER INPUT
WITH THE CHARACTERS FROM THE PTY, TAKING CARE TO ALLOW FOR
THE ASYNCHRONISM IN THE SEPARATE JOB STRUCTURES.  THIS
PROBLEM IS TRACTIBLE.

PLEASE DESCRIBE TO ME:

	(A)  WHAT KINDS OF PROGRAMS ARE LIKELY TO BE RUNNING,
AND WHAT KIND OF TERMINAL I/O THEY ARE DOING.  IN PARTICULAR,
ARE THESE PROGRAMS DOING UNUSUAL ECHOING.

	(B)  WHAT FORMATS YOU HAD IN MIND FOR THE OUTPUT
FILE.  (I WOULD INCLINE TO UNDERLINE THE USER INPUT.)
PERHAPS THIS SHOULD ALSO BE AN OPTION UNDER THE USER'S
CONTROL.

			BOB SMITH
-------